View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001060 | T99X171.00 SKB Eagle | SW Issue | public | 2020-12-21 20:28 | 2021-09-30 18:45 |
| Reporter | (ALTech) Younkwang Jung | Assigned To | (ALTech) Younkwang Jung | Due Date | |
| Priority | high | Severity | s2-severe | Reproducibility | sometimes |
| Status | closed | Resolution | fixed | ||
| Summary | 0001060: [BFX-AT100][BTF] HDMI issue ( standby on/off repeat test ) | ||||
| Description | Hi Kerwin In 15.522.42 version, there are occasional issues during standby on/off repeat test. I mentioned it as WeChat before. Two issues were observed. 1) An hdmi-noise issue was only observed on the CROSSOVER TV (often occurring). I have attached "hdmi_noise_CROSSOVER.jpg" 2) "No signal" appears on TV even though STB is standby off (occurring on test for more than 20 minutes). This issue seems to occur on all TV. I know that you already know about this issue. please let me know the current status of this issue. And please feel free to contact me if you need any help with the test. If you send me the test FW, I will send you the test results and log information. Additionally, BMT is currently in progress. if this issue is found in the BMT, we have to deal with it quickly. So we have to prepare a solution to this issue in advance. Please contact me if you have any questions. Thank you. YK.Jung | ||||
| Tags | No tags attached. | ||||
| Attach Tags | |||||
| User List |
(SW) Jacky Chiang |
|---|
|
|
|
|
|
Hi Mr. Younkwang Jung, Please verify if the test image fix the issue or not. We change the sequence and timing while doing HDMI enable/disable. So, it will take longer to see LED color changed. https://drive.google.com/drive/folders/1_1TC3VyabL1-ceZ_3ZX58zv9CxN4SyPu?usp=sharing |
|
|
Hi Kerwin I will test it and let you know the result. Thank you for your support YK.Jung |
|
|
Hi Kerwin I'll let you know the test results. Issue 1) was resolved, but issue 3) was created additionally. 1) An hdmi-noise issue was only observed on the CROSSOVER TV (often occurring). I have attached "hdmi_noise_CROSSOVER.jpg" ==> This issue has been resolved. 2) "No signal" appears on TV even though STB is standby off (occurring on test for more than 20 minutes). This issue seems to occur on all TV. ==> This issue is still happening. please check again. 3) During the Standby on/off test, an issue was observed that the STB no longer works. ( led is white , TV is no-signal , STB no longer works when the RCU is pressed ) Attach the log file. ( logcat_2020_12_23.log ) I have one question Isn't issue 2) reproduced on your side? I tested it with a two TVs here, and the issue is occurring within 50 times ( stanby on/off test ) please check it more Thank you for your support YK.Jung |
|
|
Hi Mr. Younkwang Jung, For issue (2), we don't see the same issue here. Please provide log if you have. For issue (3), it looks like Home UI is restarted due to ANR. Please provide ANR log. Thanks ! ============== logcat_2020_12_23.log =========== ... 12-23 16:48:53.472 3805 3836 E ActivityManager: ANR in com.skb.tv 12-23 16:48:53.472 3805 3836 E ActivityManager: PID: 5342 12-23 16:48:53.472 3805 3836 E ActivityManager: Reason: Broadcast of Intent { act=android.intent.action.GLOBAL_BUTTON flg=0x10000010 cmp=com.skb.tv/com.skb.google.tv.global.STBGlobalkeyBroadCastReceiver (has extras) } 12-23 16:48:53.472 3805 3836 E ActivityManager: Load: 2.11 / 2.0 / 2.0 12-23 16:48:53.472 3805 3836 E ActivityManager: CPU usage from 0ms to 7742ms later (2020-12-23 16:48:45.703 to 2020-12-23 16:48:53.445): 12-23 16:48:53.472 3805 3836 E ActivityManager: 61% 3462/android.hardware.graphics.composer@2.3-service.droidlogic: 0% user + 61% kernel 12-23 16:48:53.472 3805 3836 E ActivityManager: 15% 5342/com.skb.tv: 9.4% user + 5.6% kernel / faults: 3214 minor 14 major 12-23 16:48:53.472 3805 3836 E ActivityManager: 14% 3805/system_server: 8% user + 6.2% kernel / faults: 3294 minor 8 major 12-23 16:48:53.472 3805 3836 E ActivityManager: 8.9% 3503/PxPFileHostApp: 1.6% user + 7.2% kernel 12-23 16:48:53.472 3805 3836 E ActivityManager: 5.9% 5150/com.google.android.katniss:interactor: 3.8% user + 2% kernel / faults: 1469 minor 2 major |
|
|
Hi Kerwin Thank you for telling me about the issue (3) Then we will proceed with the test focusing on issue(2) and send the log file to you when the issue occurs. Thank you for your help YK.Jung |
|
|
Hi Kerwin I attach 3 files. The log was captured until issue(2) occurred during the test. CROSSOVER_TV.log / LG_TV.log / SAMSUNG_TV.log Please check it Thank you YK.Jung |
|
|
Hi Mr. Younkwang Jung, Could you let me know when you see the issue ? Then I could compare the difference in the log. From "CORSSOVER_TV.log", the last operation is to put STB to sleep. If it is right, then I think there is no issue to see "no signal" on TV. Thanks ! ========== CORSSOVER_TV.log ========== 12-24 09:03:39.872 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv ... 12-24 09:04:42.488 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv ... 12-24 09:04:51.287 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:05:22.674 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:07:19.218 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:08:13.572 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:08:24.489 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:08:50.092 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:09:02.635 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:09:21.380 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:09:30.361 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:10:11.533 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:10:23.581 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:10:43.223 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:10:52.819 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv .... |
|
|
Hi Kerwin we checked the state of sleep and wake-up by looking at the LED. The final LED was white. ( wake-up state ) Is there any information on the log that can check the LED status? Thank you YK.Jung |
|
|
Hi Mr. YK.Jung LED may not present current STB status. In BTF project, LED is controlled by middleware(SPTEK). We provide HAL API to set LED on/off/color. In "CORSSOVER_TV.log", I see one time that middleware doesn't ask to set LED as green while STB is going into standby mode. Please refer below for more details. ========== CORSSOVER_TV.log ========== 12-24 09:03:39.872 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:03:40.100 3547 3752 D hal_frontpanel: hal_frontpanel:HAL_FrontPanelSetLedState v102(0, 0) <== LED should be green 12-24 09:04:42.488 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:04:51.287 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:04:51.518 3547 3767 D hal_frontpanel: hal_frontpanel:HAL_FrontPanelSetLedState v102(0, 0) 12-24 09:05:22.674 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:07:19.218 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:07:19.464 3547 3775 D hal_frontpanel: hal_frontpanel:HAL_FrontPanelSetLedState v102(0, 0) 12-24 09:08:13.572 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:08:24.489 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:08:24.733 3547 3775 D hal_frontpanel: hal_frontpanel:HAL_FrontPanelSetLedState v102(0, 0) 12-24 09:08:50.092 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:09:02.635 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:09:02.866 3547 3547 D hal_frontpanel: hal_frontpanel:HAL_FrontPanelSetLedState v102(0, 0) 12-24 09:09:21.380 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:09:30.361 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:09:30.598 3547 3752 D hal_frontpanel: hal_frontpanel:HAL_FrontPanelSetLedState v102(0, 0) 12-24 09:10:11.533 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:10:23.581 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv <== I can' find message to set LED as green 12-24 09:10:43.223 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOnTv 12-24 09:10:52.819 3853 3853 W WindowManager: mBTVSleepWakeupReceiver : onReceive call turnOffTv 12-24 09:10:53.049 3547 3775 D hal_frontpanel: hal_frontpanel:HAL_FrontPanelSetLedState v102(0, 0) |
|
|
Hi Mr. YK.Jung, For issue #2, we find sometimes middle-ware will set LED even in standby mode. It might be the reason you see LED is white and TV display "no signal". We will make a workaround to avoid LED become whilte in standby mode. Thanks ! |
|
|
Hi Kerwin Thank you for considering WK. I will check again when I get the FW with workaround. and I will let you know if there is an additional test result on this issue. Thanks!! YK.Jung |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2020-12-21 20:28 | (ALTech) Younkwang Jung | New Issue | |
| 2020-12-21 20:28 | (ALTech) Younkwang Jung | Status | new => assigned |
| 2020-12-21 20:28 | (ALTech) Younkwang Jung | Assigned To | => (SW) Kerwin Chen |
| 2020-12-21 20:28 | (ALTech) Younkwang Jung | File Added: hdmi_noise_CROSSOVER.jpg | |
| 2020-12-23 14:39 | (SW) Kerwin Chen | Note Added: 0005575 | |
| 2020-12-23 14:40 | (SW) Kerwin Chen | Assigned To | (SW) Kerwin Chen => (ALTech) Younkwang Jung |
| 2020-12-23 14:40 | (SW) Kerwin Chen | Status | assigned => feedback |
| 2020-12-23 14:50 | (ALTech) Younkwang Jung | Note Added: 0005577 | |
| 2020-12-23 16:17 | (ALTech) Younkwang Jung | File Added: logcat_2020_12_23.log | |
| 2020-12-23 16:17 | (ALTech) Younkwang Jung | Note Added: 0005583 | |
| 2020-12-23 16:40 | (ALTech) Younkwang Jung | Note Edited: 0005583 | View Revisions |
| 2020-12-23 18:04 | (SW) Kerwin Chen | Note Added: 0005587 | |
| 2020-12-24 07:45 | (ALTech) Younkwang Jung | Note Added: 0005594 | |
| 2020-12-24 09:51 | (ALTech) Younkwang Jung | File Added: CROSSOVER_TV.log | |
| 2020-12-24 09:51 | (ALTech) Younkwang Jung | File Added: LG_TV.log | |
| 2020-12-24 09:51 | (ALTech) Younkwang Jung | File Added: SAMSUNG_TV.log | |
| 2020-12-24 09:51 | (ALTech) Younkwang Jung | Note Added: 0005599 | |
| 2020-12-24 09:52 | (ALTech) Younkwang Jung | Note Edited: 0005599 | View Revisions |
| 2020-12-24 15:49 | (SW) Kerwin Chen | Note Added: 0005603 | |
| 2020-12-24 16:01 | (ALTech) Younkwang Jung | Note Added: 0005604 | |
| 2020-12-24 17:04 | (SW) Kerwin Chen | Note Added: 0005606 | |
| 2020-12-28 09:13 | (SW) Kerwin Chen | Note Added: 0005622 | |
| 2020-12-28 09:40 | (ALTech) Younkwang Jung | Note Added: 0005624 | |
| 2020-12-28 10:04 | (SW) Jacky Chiang | Issue Monitored: (SW) Jacky Chiang | |
| 2021-01-20 10:47 |
|
Status | feedback => resolved |
| 2021-01-20 10:47 |
|
Resolution | open => fixed |
| 2021-09-30 18:45 | (ALTech) Younkwang Jung | Status | resolved => closed |
